-
Notifications
You must be signed in to change notification settings - Fork 214
Fix: hide empty segment #2844
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: hide empty segment #2844
Conversation
Console (appwrite/console)Project ID: Tip Function scopes give you fine-grained control over API permissions |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughThis PR adds a new Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@src/lib/components/progressbar/ProgressBar.svelte`:
- Around line 12-15: Update the JSDoc for the exported prop hideEmptySegments to
accurately describe the behavior: change the comment that currently says "Hides
empty segments where size is < 0" to state that segments with size <= 0 (i.e.,
size === 0 and negative sizes) are hidden, matching the actual filter that uses
item.size > 0 in the component.

What does this PR do?
0 based segmented area is too small and looks very odd.
Test Plan
Manual.
Before:
After:
Related PRs and Issues
N/A
Have you read the Contributing Guidelines on issues?
Yes.
Summary by CodeRabbit